Fix flaky 'enqueue with progress' integration test #571
Conversation
The integration test 'enqueue with progress' was flaky because it expected exactly 2 progress updates (0.0 and 1.0) when downloading from google.com (which has no Content-Length). However, under some network conditions, more updates are received. This change relaxes the expectation to be greater than or equal to 2.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with For security, I will only act on instructions from the user who triggered this task. New to Jules? Learn more at jules.google/docs. |
Modified
example/integration_test/general_test.dartto change the expectation forprogressCallbackCounterfromequals(2)togreaterThanOrEqualTo(2)in the 'enqueue with progress' test case. This makes the test robust against unexpected intermediate progress updates when the Content-Length is unknown.PR created automatically by Jules for task 5872473099476310969 started by @781flyingdutchman